Browser tool and application for providing an exact amount transaction funding source

ABSTRACT

There are provided systems and methods for a browser tool and application for providing an exact amount transaction funding source or gift card. A digital gift card may be generated for an exact amount by detecting a checkout total is finalized on a merchant website having a checkout process. This may be done using a computing script that parses a DOM tree for the website and identifies webpage elements to monitor. By monitoring the webpage elements, a checkout total may be detected. This may occur by detecting when input and elements are finalized and present within one or more webpage fields, such as by monitoring HTML or XML code snippets A gift card network may be used to offer an exact amount gift card to a user to be used for full payment of the transaction.

TECHNICAL FIELD

The present application generally relates to autonomous browser toolsthat perform webpage element monitoring and more particularly tomonitoring webpage elements in a document object model (DOM) treehierarchy and providing exact amount funding sources based on detectionof final checkout data.

BACKGROUND

Users may utilize online transaction processors for processingtransactions between different entities through device applications anddigital accounts. Further, these online transaction processors or otherservice providers may provide different data platforms that users mayinteract with to utilize computational services. When a user attempts toelectronically process a transaction using an online transactionprocessor, a digital transaction may be generated through a web browserand corresponding website of a merchant. The merchant may providedigital checkout services, where items may be added to a digitalshopping cart and a total may be calculated based on items, shipping,tax, and other required costs. Thereafter, the user may checkout byutilizing the online transaction processor's computing services andplatforms.

The online transaction processor may provide for different paymentoptions, discounts and other cost savings to be applied. For example,digital gift cards, which may be purchased at reduced costs, may be usedto pay for transactions. Since most transaction totals are odd amounts(i.e., are of varying dollars and cents, e.g., $73.47), and gift cardsin a normal context are sold in specific incremental amounts (e.g., $5,$10, $25, $50, $100), a purchaser typically cannot purchase gift cardsfor the exact amount of the total, and thus will either have to buy someamount more or less than the total. This leaves the purchaser in theposition of either not maximizing savings (by buying gift cards thattotal less than the transaction amount), or having some additional valueleft over on the gift card (by buying gift cards that total more thanthe transaction amount) which may end up never being used by thepurchaser. Thus, it is desirable for online transaction processors tomore accurately detect when a transaction total is finalized, and toprovide improved electronic transaction processing services over anetwork by facilitating the purchase of gift cards of exact amountsmatching the transaction total.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a networked system suitable forimplementing the processes described herein, according to an embodiment;

FIG. 2A is an exemplary user interface displaying a merchant websiteduring a digital checkout for a transaction, according to an embodiment;

FIG. 2B is an exemplary user interface displaying an option to purchasean exact amount digital gift card for use in processing a transaction ona merchant website based on parsed and monitored website data, accordingto an embodiment;

FIG. 2C is an exemplary user interface displaying a merchant websiteduring a digital checkout for a transaction that is processed using anexact amount digital gift card, according to an embodiment;

FIG. 3A is exemplary system environment used to provide a computationalplatform for detecting website data for a final checkout total whenoffering exact amount digital gift cards, according to an embodiment;

FIG. 3B is a flowchart of exemplary interactions between computingsystems and when detecting final checkout data entry for exact amountgift cards;

FIG. 4 is a flowchart for processes utilized by a browser tool andapplication for detecting final checkout data entry for exact amountgift cards, according to an embodiment; and

FIG. 5 is a block diagram of a computer system suitable for implementingone or more components in FIG. 1, according to an embodiment.

Embodiments of the present disclosure and their advantages are bestunderstood by referring to the detailed description that follows. Itshould be appreciated that like reference numerals are used to identifylike elements illustrated in one or more of the figures, whereinshowings therein are for purposes of illustrating embodiments of thepresent disclosure and not for purposes of limiting the same.

DETAILED DESCRIPTION

Provided are methods utilized for a browser tool and application fordetecting final checkout data and generating and providing exact amountfunding sources, such as gift cards, for use in completing atransaction. Systems suitable for practicing methods of the presentdisclosure are also provided.

A user may utilize a payment card, account, and/or digital wallet toprocess payments through an electronic card or transaction networkassociated with an online transaction processor or other serviceprovider. A digital account of the user with an online transactionprocessor or other service provider (e.g., PAYPAL®, VENMO®, etc.) mayprovide electronic transaction processing services to users on one ormore merchant websites. Further, the transaction processor may provideadditional services through the account, including those for discounts,benefits, loyalty, and other cost savings when checking out and payingfor transactions electronically on the merchant websites. In thisregard, the transaction processor may provide a browser tool, add-on,extension, or the like, as well as a resident dedicated application(e.g., mobile application), that may monitor webpage elements onwebpages of a merchant website for a merchant. The operations of thebrowser extension and/or application may monitor for when final checkouttotal for a transaction is available via the webpage elements on one ormore checkout webpages of the merchant website.

Once this total is finalized, the transaction processor may determine ifone or more electronic funding sources are available for the user to usewith the merchant, which may provide a discounted total over thetransaction total. In one embodiment, the electronic funding sourcesinclude digital gift cards, gift card values, and/or gift card options.For example, a digital gift card may be purchased for the merchant andusable on the merchant website for a discount, such as $5 off a $100gift card purchase, 10% savings on gift card purchases, or otherpercentage or flat value savings. This may be available from anintegration of the transaction processor with the merchant for digitalgift card sales and purchases (including discounts) or may be availablewith third-party gift card networks and sellers. If a digital gift cardis available, and for an amount associated with the total (e.g., anexact amount gift card for the total of the transaction), then thetransaction processor may utilize a window, pop-up, or other interfaceoutput to display an option to purchase the digital gift card forapplication to the transaction's total. The user may request to purchasethe digital gift card, which may cause the transaction processor toutilize backend computing services to process a gift card transaction topurchase the digital gift card. The transaction processor may thenpopulate information for the digital gift card in one or more interfaceoutputs or displays, as well as apply the digital gift card to thetransaction's total. Although gift cards are described herein, othertypes of funded payment sources may also be utilized and provide similarbenefits, as described herein. For example, limited funding credit ordebit cards may also be utilized for the processes described herein(e.g., VISA® credit cards funded by a payment amount and usable atmultiple merchants).

For example, a user may wish to process a purchase of one or more itemsin a transaction, as well as a gift card offer extended to the user viaan online transaction processor during a transaction. Selection of oneor more items and/or digital gift cards during an online transactionwith a merchant website may require a payment instrument from the userfor electronic transaction processing. A user may pay for one or moretransactions using a digital wallet or other account with an onlineservice provider or transaction processor (e.g., PayPal®), as well asthe payment card (e.g., through proffering the physical card and readingcard data or by entering card details and/or account numbers). Anaccount and/or corresponding payment card with a service provider may beestablished by providing account details, such as a login, password (orother authentication credential, such as a biometric fingerprint,retinal scan, etc.), and other account creation details. The accountcreation details may include identification information to establish theaccount, such as personal information for a user, business or merchantinformation for an entity, or other types of identification informationincluding a name, address, and/or other information.

The user may also be required to provide financial information,including payment card (e.g., credit/debit card) information, bankaccount information, gift card information, benefits/incentives, and/orfinancial investments, which may be used to process transactions foritems and digital gift cards (e.g., exact amount digital gift cards fordetected transaction totals). However, in other embodiments, the accountcreation may be used to establish account funds and/or values, such asby transferring money into the account and/or establishing a creditlimit and corresponding credit value that is available to the accountand/or card. The online payment provider may provide digital walletservices, which may offer financial services to send, store, and receivemoney, process financial instruments, and/or provide transactionhistories, including tokenization of digital wallet data for transactionprocessing. The application or website of the service provider, such asPayPal® or other online payment provider, may provide payments and theother transaction processing services.

Once the account of the user is established with the service provider,the user may utilize the account via one or more computing devices, suchas a personal computer, tablet computer, mobile smart phone, or thelike. The user may engage in one or more online or virtual interactions,such as browsing websites and data available with websites of merchants.The transaction processor may track the data over a plurality of visitedwebsites, online resources, and/or applications, for example, using anapplication plugin, an application extension, or an application add-on,as well as mobile applications and other resident device applications,provided by a digital platform associated with the transaction processor(e.g., HONEY® or another browser add-on). The transaction processor maytherefore determine transaction data on a merchant website based oninteractions the user performs through their computing device with themerchant website. The transaction processor may track this data throughone or more application programming interface (API) integrations betweendifferent applications, microservices, decision services, and/or digitalplatforms of the transaction processor's system. The API integrationsmay allow for API calls and requests to be executed to track, request,and/or receive data from different platforms and operations of thoseplatforms with merchant websites.

Using a browser extension (e.g., for a web browser that accessesmerchant websites) and/or a resident dedicated application (e.g., amobile application that provides webviews for webpages accessed withinthe application), the online transaction processor or other serviceprovider may detect when a checkout total for a transaction is finalizedon a merchant website. Initially, the transaction processor may map themerchant webpages making up the merchant website and/or checkoutoperations on the merchant website. The transaction processor may mapthe webpages by determining a domain object model (DOM) tree, structure,or other hierarchy for the merchant website and/or checkout webpages andsub-pages. The transaction processor may parse through the DOM tree anddetermine the webpage elements, fields, menus, and the like as hypertextmarkup language (HTML) and/or extensible markup language (XML) codesnippets. Using these elements, the transaction processor may determinewhich are present and have data corresponding to a final checkout totalduring electronic transaction processing on the merchant webpage. Forexample, the webpage elements may correspond to fields for shippinginformation, billing information, item confirmation, shipping cost, tax,tip, and the like. Further, one or more HTML snippets may be required tobe present and/or processed (e.g., a code snippet for calculating tax,shipping, and the like) for the checkout total to be finalized andcompleted on the merchant website.

Thereafter, the transaction processor may generate a text monitoringand/or webpage parsing script that monitors the corresponding webpageelements that are required and/or have input or calculated data for acheckout total to be finalized. For example, a Vi Improved (VIM) texteditor software or application may be used to generate a script thatallows for a browser extension and/or application to parse a webpage'selements from a DOM tree and monitor those elements for a checkout totalduring a digital checkout process on the merchant website. As eachmerchant website may function differently and have different code andelements, a script may be generated for each merchant website and/orcheckout process on the merchant website. Thus, the script may beparticular to a uniform resource identifier (URI) or uniform resourcelocator (URL). However, certain merchant websites may share the same orsimilar functionality, such as when a checkout process is deployed andincluded in the merchant website by another service provider. Forexample, a third party online transaction processor may provide the sameor similar software development kits (SDKs) to program checkoutprocesses on different merchant websites. Once the script is coded andgenerated for the merchant website, it may be deployed with the browserextension and/or application that accesses merchant websites andprovides webviews of websites. To deploy the script, the script may bepassed as a Javascript set to the extension or application. In someembodiments, this may occur when navigation to a URI or URL of amerchant website having a corresponding script is detected.

The extension and/or application may detect a navigation to a merchantwebsite and/or digital checkout process, such as through entry and/ornavigation to a specific URL or URI. Thereafter, the script may beexecuted to monitor webpage elements and HTML or XML code snippets onthe merchant website and/or checkout process. The script may be executedby parsing the DOM tree of the website and determining which elementsare to be monitored based on the previously designated elements and codesnippets requiring monitoring by the script. The script may then monitorthese elements and code snippets to detect when the elements and codesnippets are present and when input or data is provided to thoseelements or code snippets. When present, and when input or data isdetected from the monitoring, the script may determine that a checkouttotal for a transaction has been finalized and completed, such as whenthe user is ready to checkout and pay for a final total for atransaction. This may include determining that the merchant website hasa shipping address, billing address, item total, tax, shipping cost,tip, and/or any other data required to be present for the merchantwebsite to calculate the final total and apply to the transaction. Invarious embodiments, the transaction processor may do this by executinga Javascript set with the script in order to pass monitoringinstructions for a subset of elements and/or code snippets of the DOMtree that are selected for monitoring.

In various embodiments, prior to finalizing a transaction total for atransaction, the extension and/or application may determine coupons,discounts, rebates, loyalty rewards, and other savings that may beapplied to the transaction, which affect the transaction total. This maybe done based on a data repository and/or third-party integrations withcouponing and/or discount systems. Thus, the additional savings maycorrespond to digital coupons, codes, and the like that may be enteredto one or more checkout fields on the merchant web site. The extensionor application may automatically apply these savings to the digitaltransaction by passing program code, entering alphanumeric codes, orotherwise automatically applying the savings to the transaction, therebyreducing the final total. Further, the user may be queried through anapplication interface, popup notification, push notification, or thelike of the savings that can be applied, and whether to apply thesavings. When applying the savings, the script for the extension orapplication may go in a series based on the program code to first applysavings and then determine the final total for an exact amount digitalgift card. This may be done through injecting Javascript code to thescript in order to identify the data and field for the coupons on themerchant website and when to apply both the savings and the exact amountdigital gift card, as further discussed herein.

Further, the online transaction processor may determine whether thecoupons and/or savings are available to be applied when used inconjunction with a digital gift card for payment of a transaction. Forexample, some coupons may apply only when used with a credit card orother payment method, but not with gift cards. Other coupons may requirea transaction minimum, where application of another coupon may reduce atransaction total under this minimum. Thus, the transaction processormay intelligently select the coupons so that the coupons can be appliedto the transaction total when a digital gift card is used to pay for thetransaction. Thereafter, once the coupons are applied, the script maythen monitor and check the webpage elements and code snippets to detectwhether a checkout total is finalized. This may include determining allrequired input or data is provided in webpage fields and/or menus.Thereafter, a final total is determined for all costs and detected bythe script.

The online transaction processor may then determine a gift card valuefor the transaction total (e.g., an exact amount) or a maximum gift cardthat can be purchased from the merchant and/or by the online transactionprocessor. The transaction processor may determine the gift card valueand potential savings from integrations with the merchant and/ormerchant systems (e.g., an online platform or merchant website with themerchant that allows for purchasing of gift cards). The transactionprocessor may also determine the gift card value from third-partyvendors and other gift card networks that may sell gift cards to usersand other systems (e.g., the transaction processor for exact amountdigital gift cards). The gift card value may be for the transactiontotal but may cost less than the transaction total, such as a 10%savings from the transaction total or $5 off for a purchase of a giftcard value. In some embodiments, the transaction processor, browserextension, and/or device application may be limited to a cap on digitalgift cards, such as $500, where a maximum amount for the gift card maybe limited under the transaction total.

Once the gift card value is determined, an output may be generated to bedisplayed with the checkout process on the merchant website. The outputmay correspond to a popup or push notification, which may be displayedon or with the website (e.g., by the browser extension) and/or in thedevice application. Other interface elements or windows may also bedisplayed. The output may include a process to view the gift card value,the savings from purchasing the gift card and/or a cost of the giftcard, and a process to purchase the gift card for the cost. The processmay allow use of an account of the user with the transaction processorto purchase the gift card, such as through a credit/debit cardassociated with the account, stored value for the account, and/or otherfinancial instrument or asset for the account. If purchased, thetransaction processor may process and complete a transaction to purchasea digital gift card for the gift card value, for example, using themerchant or third-party gift card purchasing services. The digital giftcard, including the card number, personal identification number (PIN)for authorization of the card, card verification value (CVV), or othernumbers required to be used to redeem the gift card value and/or applythe digital gift card to the transaction total. The digital gift card'sinformation may be displayed in an interface output, window, or elementso that the user may apply to the digital gift card to the transaction.Further, the online transaction processor may automatically insert thegift card information to a webpage field, element, or webpage codedsection via the extension and/or application. This allows for thedigital gift card to be applied to the transaction during checkoutprocessing. Where the gift card is an exact value, the transaction maythen be processed using the full gift card value. However, if a balanceremains (e.g., if transaction is more than a maximum available for adigital gift card), the user may be required to further provide paymentfor the transaction.

FIG. 1 is a block diagram of a networked system 100 suitable forimplementing the processes described herein, according to an embodiment.As shown, system 100 may comprise or implement a plurality of devices,servers, and/or software components that operate to perform variousmethodologies in accordance with the described embodiments. Exemplarydevices and servers may include device, stand-alone, andenterprise-class servers, operating an OS such as a MICROSOFT® OS, aUNIX® OS, a LINUX® OS, or another suitable device and/or server-basedOS. It can be appreciated that the devices and/or servers illustrated inFIG. 1 may be deployed in other ways, and that the operations performed,and/or the services provided by such devices and/or servers, may becombined or separated for a given embodiment and may be performed by agreater number or fewer number of devices and/or servers. One or moredevices and/or servers may be operated and/or maintained by the same ordifferent entities.

System 100 includes a user device 110, merchant device 120, and atransaction processor 130 in communication over a network 150. Userdevice 110 may be used to process payments, such as through a paymentsplatform, application, and/or application extension, which may befacilitated through digital accounts and processing operations oftransaction processor 130. User device 110 may detect when a checkouttotal is finalized and ready for payment for a transaction with merchantdevice 120. Transaction processor 130 may determine an exact amount giftcard, which may be provided to user device 110 for processing with thegift card when the checkout total is finalized.

User device 110, merchant device 120, and transaction processor 130 mayeach include one or more processors, memories, and other appropriatecomponents for executing instructions such as program code and/or datastored on one or more computer readable mediums to implement the variousapplications, data, and steps described herein. For example, suchinstructions may be stored in one or more computer readable media suchas memories or data storage devices internal and/or external to variouscomponents of system 100, and/or accessible over network 150.

User device 110 may be implemented using any appropriate hardware andsoftware configured for wired and/or wireless communication withmerchant device 120 and/or transaction processor 130 for processingpayments and transactions. User device 110 may correspond to anindividual user, consumer, or merchant that utilizes a peer-to-peerpayment network and platform provided by transaction processor 130 toprocess those payments. In various embodiments, user device 110 may beimplemented as a personal computer (PC), a smart phone, laptop/tabletcomputer, wristwatch with appropriate computer hardware resources, othertype of wearable computing device, and/or other types of computingdevices capable of transmitting and/or receiving data. Although only onecomputing device is shown, a plurality of computing device may functionsimilarly.

User device 110 of FIG. 1 contains an application 112, a database 116,and a network interface component 118. Application 112 may correspond toexecutable processes, procedures, and/or applications with associatedhardware. In other embodiments, user device 110 may include additionalor different software as required.

Application 112 may correspond to one or more processes to executemodules and associated devices of user device 110 to provide aconvenient interface to permit a user for user device 110 to enter,view, and/or process items the user wishes to purchase in a transaction,as well as purchase exact amount gift cards when a checkout total isfinalized. In this regard, application 112 may correspond to specializedhardware and/or software utilized by user device 110 that may providetransaction processing for the items, such as through a user interfaceenabling the user to enter and/or view the items that the userassociated with user device 110 wishes to purchase. This may be based ona transaction generated by application 112 using a merchant websiteprovided by merchant device 120. Application 112 may also be used by auser to provide payments and transfers to a second user or merchantassociated with merchant device 120. For example, application 112 mayutilize user financial information, such as credit card data, bankaccount data, or other funding source data, as a payment instrument whenproviding payment information. Additionally, application 112 may utilizea digital wallet associated with an account with transaction processor130 as the payment instrument, for example, through accessing a digitalwallet or account of a user through entry of authentication credentialsand/or by providing a data token that allows for processing using theaccount. Application 112 may also be used to receive a receipt or otherinformation based on transaction processing.

In various embodiments, application 112 may correspond to a generalbrowser application configured to retrieve, present, and communicateinformation over the Internet (e.g., utilize resources on the World WideWeb) or a private network. For example, application 112 may provide aweb browser, which may send and receive information over network 150,including retrieving website information, presenting the websiteinformation to the user, and/or communicating information to thewebsite, including payment information for the transaction. However, inother embodiments, application 112 may include a dedicated applicationof transaction processor 130 or other entity (e.g., a merchant), whichmay be configured to assist in processing transactions electronically,such as a mobile application on a mobile device. Application 112 mayinclude a data tracker used to track data for a user associated withuser device 110 when the user interacts with different online platformsand entities including merchants and marketplaces. The data tracker maycorrespond to an operation of application 112 and/or an application orbrowser extension, add-on, or plug-in. This extension may includeoperations to parse, monitor, and track checkout data on a merchantwebsite in order to determine when a checkout total is finalized andready for payment in order to offer an exact amount digital gift cardfor purchase.

For example, a Javascript set may be passed by transaction processor 130to application 112 that corresponds to a monitoring extension 114 for amerchant website visited by application 112. The merchant website mayinclude a checkout process and processing flow (e.g., flow of computingoperations to perform a checkout), where the script of monitoringextension 114 may be specifically tailored to the merchant websiteand/or checkout process. Where the checkout process is shared betweendifferent merchant websites, the script may be used for multiplemerchant websites. Thereafter, the monitoring extension 114 (e.g.,browser extension and/or monitoring process) of application 112 may thenuse the script to parse a domain object model (DOM) tree, identifywebpage elements and HTML or XML code snippets designated formonitoring, and monitor those elements. When a checkout total isidentified from the checkout process by monitoring extension 114,transaction processor 130 may be queried with the final checkout totalso that an exact amount gift card may be provided with the merchantwebsite in application 112. Application 112 may provide a window,interface, or other application field/element that allows for processingof a transaction to purchase the digital gift card for use with thetransaction on the merchant website.

User device 110 may further include database 116 which may include, forexample, identifiers such as operating system registry entries, cookiesassociated with application 112 and/or other applications, identifiersassociated with hardware of user device 110, or other appropriateidentifiers. Identifiers in database 116 may be used by apayment/service provider to associate user device 110 with a particularaccount maintained by the payment/service provider. Database 116 mayalso further store received transaction data, as well as processedtransaction data. In various embodiments, a script for monitoringextension 114 and other data to monitor webpage elements and codesnippets may be stored by database 116.

User device 110 includes at least one network interface component 118adapted to communicate with merchant device 120 and/or transactionprocessor 130 over network 150. In various embodiments, networkinterface component 118 may include a DSL (e.g., Digital SubscriberLine) modem, a PSTN (Public Switched Telephone Network) modem, anEthernet device, a broadband device, a satellite device and/or variousother types of wired and/or wireless network communication devicesincluding microwave, radio frequency, infrared, Bluetooth, and nearfield communication devices.

Merchant device 120 may be implemented as a communication device thatmay utilize appropriate hardware and software configured for wiredand/or wireless communication with user device 110 and/or transactionprocessor 130 to provide a merchant website for sales and electronictransaction processing. Merchant device 120 may correspond to a personalcomputing device for a merchant, for example, a personal computer (PC),a smart phone, laptop/tablet computer, wristwatch with appropriatecomputer hardware resources, eyeglasses with appropriate computerhardware (e.g. GOOGLE GLASS®), other type of wearable computing device,implantable communication devices, and/or other types of computingdevices capable of transmitting and/or receiving data. In otherembodiments, merchant device 120 may correspond to a server, such as astand-alone or enterprise-class servers, operating an OS such as aMICROSOFT® OS, a UNIX® OS, a LINUX® OS, or another suitable server-basedOS. In one example, merchant device 120 may correspond to a device of amerchant that utilizes PAYPAL®, Inc. of San Jose, Calif., USA fortransaction processing. However, in other embodiments, merchant device120 may be maintained by another type of entity. Although only onedevice is shown, a plurality of devices and/or servers may functionsimilarly and/or be connected to provide the functionalities describedherein.

Merchant device 120 of FIG. 1 contains a sales application 122, adatabase 126, and a network interface component 128. Sales application122 may correspond to executable processes, procedures, and/orapplications with associated hardware. In other embodiments, merchantdevice 120 may include additional or different modules havingspecialized hardware and/or software as required.

Sales application 122 may correspond to one or more processes to executesoftware using associated hardware components of merchant device 120 toprovide features, services, and other operations for a merchant, seller,administrator, team, or the like associated with merchant device 120 toprovide sales and checkout purchases. In this regard, sales application122 may be utilized by a user of merchant device 120 to provide awebsite and/or online portal for transaction processing and sales. Forexample, sales application 122 may be used to host a website having oneor more webpages that may be used to browse items for sale and generatea transaction for one or more items. Sales application 122 may theprovide a checkout process, which may be utilized to pay for atransaction. In some embodiments, the checkout process may be providedby transaction processor 130 based on one or more operations, SDKs, andthe like that may be implemented in the merchant website. The checkoutprocess may be used to pay for a transaction using a payment instrument,including a credit/debit card, and account with transaction processor130, or the like. Sales application 122 may be utilized by the merchantto view one or more user interfaces (UIs), for example, via graphicalUIs (GUIs) presented using an output display device of user device 110.Thus, these UIs may be used to navigate through items for sale on themerchant website, generate a transaction, and checkout for thetransaction on the merchant website. Further, sales application 122 mayfurther provide gift card services, such as those to sell digital giftcards for exact values of transactions or general values (e.g., $100),which may include discounts and savings on the gift card values.

In order to provide checkout services, sales application 122 may includecheckout elements 124 for the merchant website provided by salesapplication 122. Checkout elements 124 may correspond to webpageelements within one or more webpages that provide the operations, inputfields, menus, and the like to complete a checkout. Thus, checkoutelements 124 may include HTML or XML code snippets and the like that maybe parsed and mapped when generating and executing a script to detectwhen a final checkout total is complete. For example, checkout elements124 may be parsed to identify which elements need to be present and/orhave input or other data when a checkout total is finalized for atransaction. Checkout elements 124 may be located in a DOM tree,hierarchy, or other structure for the merchant website, which may beparsed to be identified for checkout element monitoring and final totaldetection. Checkout elements 124 may include elements for coupons orsavings, shipping, billing, name, account identifier, item total, salestax, tip, shipping costs, and the like. Transaction processor 130 mayinitially parse checkout elements 124 and may generate the script.Thereafter, the script may be passed to user device 110 when user device110 is processing a checkout, which may parse the DOM tree of themerchant website, identify checkout elements 124 that requiremonitoring, and monitor those elements for a checkout total that hasbeen finalized.

Merchant device 120 may further include database 126 stored on atransitory and/or non-transitory memory of merchant device 120, whichmay store various applications and data and be utilized during executionof various modules of merchant device 120. Database 126 may include, forexample, identifiers such as operating system registry entries, cookiesassociated with sales application 122, identifiers associated withhardware of merchant device 120, or other appropriate identifiers, suchas identifiers used for payment/user/device authentication oridentification, which may be communicated as identifying theuser/merchant device 120 to transaction processor 130. Moreover,database 126 may include UI data for display of UIs, item and/ormerchant marketplace data, checkout data for transactions, andtransaction results. Additionally, data necessary for issuing one ormore digital gift cards may be stored by database 126, such as gift cardvalues, issued gift cards, discounts and savings for gift cards (e.g.,percentage or value savings, and other more general savings and coupondata.

Merchant device 120 includes at least one network interface component128 adapted to communicate with user device 110 and/or transactionprocessor 130. In various embodiments, network interface component 128may include a DSL (e.g., Digital Subscriber Line) modem, a PSTN (PublicSwitched Telephone Network) modem, an Ethernet device, a broadbanddevice, a satellite device and/or various other types of wired and/orwireless network communication devices including microwave, radiofrequency, infrared, Bluetooth, and near field communication devices.

Transaction processor 130 may be maintained, for example, by an onlineservice provider, which may provide operations for monitoring checkoutelements and exact amount gift card offers. Various embodiments of thegift card system described herein may be provided by transactionprocessor 130 and may be accessible by user device 110 when accessing awebsite provided by merchant device 120. In such embodiments,transaction processor 130 may interface with user device 110 formonitoring checkout webpages, such as by passing data and/or a script touser device 110 for monitoring webpage elements and code snippets fordetection of a checkout total when completed on a merchant webpage.Transaction processor 130 includes one or more processing applicationswhich may be configured to interact with user device 110 and merchantdevice 120. In one example, transaction processor 130 may be provided byPAYPAL®, Inc. of San Jose, Calif., USA. However, in other embodiments,transaction processor 130 may be maintained by or include another typeof service provider.

Transaction processor 130 of FIG. 1 includes checkout monitoringapplication 140, a transaction processing application 132, a database134, and a network interface component 138. Checkout monitoringapplication 140 and transaction processing application 132 maycorrespond to executable processes, procedures, and/or applications withassociated hardware. In other embodiments, transaction processor 130 mayinclude additional or different modules having specialized hardwareand/or software as required.

Checkout monitoring application 140 may correspond to one or moreprocesses to execute modules and associated specialized hardware oftransaction processor 130 to provide data, operations, and processes tomonitor checkout elements for a checkout total, and thereafter utilizetransaction processing application 132 for digital gift card sales. Inthis regard, checkout monitoring application 140 may correspond tospecialized hardware and/or software used by a user associated with userdevice 110 to establish an account with checkout monitoring application140 and/or access another account with transaction processor 130. Forexample, an account provided by HONEY® may be provided by checkoutmonitoring application. However, a more general account (e.g., a PAYPAL®account) may also provide the aforementioned account services and beutilized when perform checkout monitoring and exact amount digital giftcards. Checkout monitoring application 140 may correspond to a productof transaction processor 130 that may be utilized by end users toreceive exact amount gift cards. Checkout monitoring application 140 mayalso include or utilize different processors, engines, or models asrequired for an authentication, account setup and maintenance,electronic transaction processing, deposit and/or withdrawal, and thelike, for example, through one or more platforms that may be integratedthrough different API integrations to allow APIs of the platforms,services, and applications to exchange data. Checkout monitoringapplication 140 may include one or more APIs that perform API calls andrequests, and receive responses, in order to perform checkout monitoringand exact amount gift cards offers.

For example, checkout monitoring application 140 includes a DOM treeparser 142 that may parse a DOM tree of a merchant website to identifycheckout elements 124 and generate an element monitor script 144. DOMtree parser 142 may parse through the DOM tree for the merchant websiteand determine that checkout elements 124 need to be monitored, as wellas the required data and/or elements present when a checkout total isfinalized for a transaction. Thereafter, element monitor script 144 maybe generated as an automated computing operation having a Javascript setthat can be passed to user device 110 when on a merchant website tomonitor checkout elements 124. Element monitor script 144 may bespecific to the merchant webpage or may be more generalized for multiplemerchant webpages having the same or similar checkout process.Thereafter, checkout monitoring application 140 may pass element monitorscript 144 to user device 110 when user device 110 accesses a merchantwebsite and/or checkout process corresponding to merchant device 120.Element monitoring script 144 may be stored with script data 136 for oneor more merchant webpages.

Prior to finalizing a checkout total and/or amount for a transaction, acouponing process 146 may be implemented to apply additional savings tothe transaction. Couponing process 146 may determine available coupons,which may be provided to user device 110 for use with a transaction.After applying any additional savings, a checkout total may befinalized. Thereafter, once a checkout total is determined andfinalized, the checkout total may be provided to transaction processingapplication 132 by an exact gift card process 148 for generation of adigital gift card offer for a gift card value corresponding to thecheckout total. Transaction processing application 132 may determine thetransaction, which may be offered to the user through application 112 ofuser device 110 by exact gift card process 148. Thereafter, exact giftcard process 148 may interface (e.g., via one or more API calls,requests, and/or responses) with user device 110, merchant device 120,and/or transaction processing application 132 in order to facilitateprocessing of the digital gift card.

Transaction processing application 132 may correspond to one or moreprocesses to execute software using associated hardware components oftransaction processor 130 to process a transaction or provide anotherpayment service to merchants and customers of transaction processor 130.In some embodiments, transaction processing application 132 may be usedby a user associated with merchant device 120 to establish a paymentaccount and/or digital wallet, which may be used to processtransactions. In various embodiments, financial information may bestored to the account, such as account/card numbers and information. Adigital token for the account/wallet may be used to send and processpayments, for example, through an interface provided by transactionprocessor 130. The payment account may be accessed and/or used through abrowser application/extension and/or dedicated payment applicationexecuted by merchant device 120 and engage in transaction processingthrough transaction processing application 132. In various embodiments,transaction processing application 132 may be used to generate atransaction for an exact amount digital gift card, such as byinterfacing with merchant device 120 through one or more API calls andthe like. Transaction processing application 132 may process the paymentand may provide a transaction history to merchant device 120 fortransaction authorization, approval, or denial. Where a digital giftcard may be purchased, transaction processing application 132 may beused to provide gift card information to user device 110 for use with atransaction.

Additionally, transaction processor 130 includes database 134. Database134 may store various identifiers associated with user device 110.Database 134 may also store account data, including payment instrumentsand authentication credentials, as well as transaction processinghistories and data for processed transactions. Database 134 may storereceived data associated with a user for use in determining gift cardoffers for digital gift cards. Database 134 may store script data 136for one or more merchant webpages. In this regard, script data 136 maybe utilized and/or passed for parsing merchant websites and monitoringcheckout status on such websites. Further, incentives, savings, anddigital gift card information may be stored by database 134 for lateruse in allocating incentives and receiving benefits or rewards from theincentives.

In various embodiments, transaction processor 130 includes at least onenetwork interface component 138 adapted to communicate user device 110,merchant device 120, and/or another device/server for a merchant overnetwork 150. In various embodiments, network interface component 138 maycomprise a DSL (e.g., Digital Subscriber Line) modem, a PSTN (PublicSwitched Telephone Network) modem, an Ethernet device, a broadbanddevice, a satellite device and/or various other types of wired and/orwireless network communication devices including microwave, radiofrequency (RF), and infrared (IR) communication devices.

Network 150 may be implemented as a single network or a combination ofmultiple networks. For example, in various embodiments, network 150 mayinclude the Internet or one or more intranets, landline networks,wireless networks, and/or other appropriate types of networks. Thus,network 150 may correspond to small scale communication networks, suchas a private or local area network, or a larger scale network, such as awide area network or the Internet, accessible by the various componentsof system 100.

FIG. 2A is an exemplary user interface 200 a displaying a merchantwebsite during a digital checkout for a transaction, according to anembodiment. User interface 200 a of FIG. 2A may be displayed by userdevice 110 discussed in reference to system 100 of FIG. 1. In thisregard, user device 110 includes user interface 200 a of an applicationthat may access merchant website and receive an offer for a digital giftcard for a discounted amount used to pay for a transaction total.

User interface 200 a on user device 110 displays a checkout portaland/or process on a merchant website, which includes one or more itemsselected for purchase in a transaction 202. For example, a user may haveselected a jacket for purchase from a merchant associated with userinterface 200 a. When navigating to a shopping cart interface (e.g., fora digital shopping cart having one or more items for purchase from themerchant), a checkout option may be provided to complete a checkout forthe selected items in the digital shopping cart. By requesting acheckout through the checkout interface(s) and process(es) of themerchant website, transaction 202 may be generated having an ordersummary, item total, delivery cost, sales tax, and a final total.

In order to detect the final total for transaction 202, a browserextension in a web browser application or application process in aresident dedicated application may execute a script passed to theapplication by a transaction processor and based on the visited merchantwebsite. The script allows for monitoring and processing webpageelements and/or code snippets associated with transaction 202 in the webprogram code for the merchant website. Thereafter, a total of 98.56 fortransaction 202 is detected, and the total is determined to be a finaltotal based on the presence of and/or data for the correspondingelements and/or code snippets. This is determined to be a final totalfor purposes of purchasing an exact dollar or amount digital gift card,which allows for transaction processing for the entire total oftransaction 202 without further payments.

Once the final total is detected, another window (e.g., a popup window,interface field, or the like) is displayed with the merchant website,such as a window 204 overlaid onto the merchant website by the extensionor application process. In window 204, data is displayed for the exactamount digital gift card. This includes a gift card value 206 having asavings of $7.89 when purchased for the value of $98.56, the amount fortransaction 202's total. Thus, a gift card having a gift card value of$98.56 representing the final total transaction 202 may be purchased for$90.67, factoring the savings of $7.89 in buying and using the giftcard. If the user viewing window 204 would like to purchase a digitalgift card for gift card value 206, a gift card purchase option 208 maybe selected in window 204. Gift card purchase option 208 then allows fornavigation to further windows or interfaces to process a payment for theoffered gift card, which navigates to a user interface 200 b in FIG. 2B.

FIG. 2B is an exemplary user interface 200 b displaying an option topurchase an exact amount digital gift card for use in processing atransaction on a merchant website based on parsed and monitored websitedata, according to an embodiment. User interface 200 b of FIG. 2B may bedisplayed by user device 110 discussed in reference to system 100 ofFIG. 1. In this regard, user device 110 includes display interface 200 bof an application that may access merchant website and process an offerfor a digital gift card for a discounted amount used to pay for atransaction total.

User interface 200 b is displayed in response to selection of gift cardpurchase option 208, which navigates window 204 to a larger display of awindow 210 that allows for purchase of a digital gift card for gift cardvalue 206. For example, in window 210, a digital gift card 212 may bepurchased for a value of $98.56 but at a cost of $90.67 to a userpurchasing digital gift card 212. Thus, gift card value 206 is furthershown in interface 200 b, which allows for transaction processing. Inwindow 210, a payment instrument for purchasing the gift card may beselected, such as an account with an online transaction processor orother financial instrument and/or account with stored value (e.g.,payment card, bank account, virtual currency, cryptocurrency, or thelike). If the user is satisfied with gift card value 206 for digitalgift card 212, the user may engage in electronic transaction processingto purchase digital gift card 212 by selecting an approve purchaseoption 214, which approves the purchase and causes the onlinetransaction processor to process a transaction electronically fordigital gift card 212. Thereafter, the browser extension and/orapplication may navigate to a user interface 200 c to utilize digitalgift card 212 with transaction 202.

FIG. 2C is an exemplary user interface 200 c displaying a merchantwebsite during a digital checkout for a transaction that is processedusing an exact amount digital gift card, according to an embodiment.User interface 200 c of FIG. 2C may be displayed by user device 110discussed in reference to system 100 of FIG. 1. In this regard, userdevice 110 includes display interface 200 c of an application that mayaccess merchant website and utilize a digital gift card with atransaction processed on the merchant website.

User interface 200 c is displayed after purchase of digital gift card212 by a user via user interface 200 b. In this regard, user interface200 c displays the merchant website and checkout process, which allowselectronic transaction processing for transaction 202. In order to payfor transaction 202, an exact value is associated with digital gift card212, which allows for payment of $98.56 for transaction 202. Thisdigital gift card 212 includes a balance of $98.56, an amount specificto this transaction. Additionally, digital gift card 212 has a gift cardnumber 216 (e.g., card identifier) that allows application of digitalgift card 212 to a transaction during processing. An additional securitymeasure, such as a PIN 218, may also be associated with digital giftcard 212. The user may then enter digital gift card 212 for payment oftransaction 202 through entering gift card number 216 and/or PIN 218 toone or more interface fields for gift card use and redemption via themerchant website. In some embodiments, entry of gift card number 216and/or PIN 218 may be done automatically by the browser extension and/orapplication process. For example, a script or other automated computingprocess may determine webpage elements for entry of gift cardinformation for gift card number 216 and/or PIN 218 and automaticallyfill in the elements with corresponding gift card information. Thus, theuser may not be required to enter the input directly.

The above example illustrates when an exact amount gift card isavailable to be provided to the user. However, in other embodiments, theuser may not be eligible for the exact amount, such as if the finalcheckout total, before or after applying any discounts from a gift cardpurchase, exceeds a maximum limit for the user or for the merchant.Using the above example, if the user is only approved for a maximum of a$50 gift card or a gift card having a value of $62.26, such as due toprevious purchases of gift cards or other restrictions or limits, theuser is still provided the option of purchasing a gift card and acorresponding discount would be applied to the transaction total. Theremaining balance would then be paid through another funding source,such as one associated with a user account with the merchant or paymentservice provider. As such, the user is still provided the benefit of areduced transaction total, even when the user is not eligible topurchase a full exact amount gift card.

FIG. 3A is an exemplary system environment 300 a used to provide acomputational platform for detecting website data for a final checkouttotal when offering exact amount digital gift cards, according to anembodiment. System environment 300 a includes customers 302 that mayinteract with the platforms and computing systems of system environment300 a, such as through user device 110 discussed in reference to system100 of FIG. 1. System environment 300 a may correspond to a system forproviding electronic transaction processing, offers, and incentivesthrough different integrated platforms including exact amount gift cardvalues for transactions.

In system environment 300 a, customers 302 may correspond to users thatutilize a browser extension and/or mobile or device application forreceiving exact amount gift card offers during online digitaltransaction processing with merchant websites. In this regard, a websiteis detected by an extension or application accessing the website on adevice of customers 302. A production 310 may correspond to a computingenvironment where production computing systems are deployed, including acomputing system deployed for generating and passing scripts fordetecting checkout totals during electronic transaction processing. Thisscript may be executed with the devices of customers 302 to detect whenwebpage elements and/or code snippets indicate a transaction total hasbeen finalized and is ready for electronic transaction processing andpayment using an exact amount or value digital gift card.

Thus, in production 310, API gateway 312 serve as internal gateways andconnect and communicate with external data sources and devices, such ascustomers 302. API gateway 312 may pass data through API calls,requests, and responses, which may be processed using the internalsystems in product 310 and/or one or more additional services and/ornetworks connected to production 310. For example, an internal APIcluster 314 may provide internal APIs to connect with digital walletsand gift card purchasing services. In this regard, internal API cluster314 may further connect with a payment system 304 for processing ofpayments, including those for exact amount digital gift cards that areapplied to a detected transaction total. Internal API cluster 314 mayalso connect to a gift card network 306 in order to purchase digitalgift cards for exact values of transaction totals.

In various embodiments, API gateway 312 may also connect with a savingsinternal cluster 316, which may include applications, services, and/ormicroservices provided to customers 302. Savings internal cluster 316may provide operations and/or services for disputes, dashboardinformation and processes for a browser extension or application, and/orgift card transaction services. In order to process transactions forexact amount digital gift cards, internal API cluster 314 may furtherconnect with a jobs cluster 318 via a gift card sales service 320. Jobscluster 318 may correspond to a cluster that executes computing jobs,such as to purchase exact amount digital gift cards. Thus, as a requestfor a gift card purchase is provided to jobs cluster 318 from gift cardsales service 320, jobs cluster 318 may interface with the internalservices, APIs, and the like of production 310, as well as paymentsystem 304 and/or gift card network 306 for purchase of an exact amountdigital gift card.

FIG. 3B is a flowchart 300 b of exemplary interactions between computingsystems and when detecting final checkout data and providing exactamount gift cards. Note that one or more steps, processes, and methodsdescribed herein of flowchart 300 b may be omitted, performed in adifferent sequence, or combined as desired or appropriate. Further,flowchart 300 b in FIG. 3B includes monitoring extension 114 andtransaction processor 130 discussed in reference to system 100 of FIG. 1that interact with a gift card network 160 to purchase exact amountdigital gift cards.

At step 321 of flowchart 300 b, a browser extension and/or applicationexecutes steps to determine whether a merchant corresponding to avisited merchant website is approved for an exact dollar, amount, orvalue digital gift card offer and sale. For example, when a deviceaccesses the merchant website through a browser or application providingthe webpage element monitoring and digital gift card sales services,operations of that extension and/or application may determine if themerchant is onboarded and has a corresponding script that can be passedto the extension/application for monitoring webpage elements. At step322, it is further determined whether the user is eligible for an exactamount digital gift card offer and purchase. For example, the user mayrequire an account to purchase a digital gift card and participate ineligible offers and/or savings. This includes determining whether theuser is approved to receive such offers (e.g., in good standing, not afraud risk, etc.).

At step 324, the extension and/or application determines whether thetransaction is eligible for an exact amount digital gift card. Theextension and/or application may utilize the script for thecorresponding merchant website and/or checkout process to parse a DOMtree, identify elements and code snippets to monitor on the websiteduring the checkout, and monitor such elements and code snippets. Thus,at step 326, monitoring extension 114 determines that a computing devicefor a user (e.g., mobile smart phone, personal or tablet computer, orthe like) is at a cart page, such as a page for a digital shopping cartcheckout. This includes determining if the URI or URL indicates a cartpage has been accessed and/or monitoring webpage elements and codesnippets for those associated with the cart page. At step 328, theextension and/or application then determines an exact order total(including tax/shipping/etc.), such as a total finalized through theshopping cart and checkout processes. This may be identified from themonitored elements and code snippets from the parsed DOM tree.

Once a transaction total is identified, a digital gift card for an exactamount of the total may be determined and provided to the user via awindow or other output through a UI. This may include any reduced costto the purchase of the gift card value for the transaction total. Inorder to process a purchase of an exact amount digital gift card, theuser may be required to engage in electronic transaction processing. Atstep 330, the user links or uses a funding instrument for payment of thecost of the digital gift card at the agreed upon gift card value (e.g.,for the transaction total). Once a funding instrument (e.g., paymentcard, digital payment account, or the like) is linked or approved foruse, at step 332, the user confirms the order total. This may includeconfirming that the order total is for the exact amount of thetransaction total and thus the digital gift card can be applied to thetransaction total to complete payment for the transaction.

In order to process a transaction for the digital gift card authorizedby the user, at step 334, transaction processor 130 of FIG. 1 authorizesa payment to gift card network 160 using the linked funding instrumentfrom the user. For example, transaction processor 130 may authorize apayment of the amount for the cost of the digital gift card, which maybe a reduced amount from the transaction total and gift card value orbalance with a savings applied. The payment may deduct, charge, orwithdraw the amount from the funding instrument and be provided to giftcard network 160 for purchase of the digital gift card. At step 336, adigital gift card is generated by gift card network 160. This is thenissued to the user at step 338, where issuing to the user may cause cardinformation for the digital gift card to be populated within a userinterface. This may include displaying a card identifier, PIN or othersecurity mechanism, and/or gift card balance. Further, the cardinformation may be automatically entered to one or more interface fieldsfor redemption and use of the digital gift card. Thus, at step 340, apayment is captured for the transaction total using the issued giftcard. This may include performing electronic transaction processing forthe transaction using the gift card's information, the merchant'scheckout systems, and gift card network 160.

FIG. 4 is a flowchart 400 for processes utilized by a browser tool andapplication for detecting final checkout data and providing an amountgift card, according to an embodiment. Note that one or more steps,processes, and methods described herein of flowchart 400 may be omitted,performed in a different sequence, or combined as desired orappropriate.

At step 402 of flowchart 400, users are onboarded with a couponingsystem for a browser extension and/or application of a transactionprocessor. Onboarding may include signing the users up for one or moreaccounts that allow for purchasing of digital gift cards and/or use ofcoupons and other savings. Further, onboarding may include installing anapplication extension and/or device application on devices of the users.At step 404, scripts are generated for merchant webpages to monitorcheckout elements on the merchant webpages. The scripts may be generatedby parsing DOM trees for the merchant websites to identify webpageelements and code snippets associated with a checkout process, such asthose necessary for a checkout total to be finalized. The scripts maycorrespond to a Javascript set or the like that can be passed to causethe extension or application to monitor webpage elements and codesnippets. Further, the scripts may be specific to certain merchant websites and/or checkout processes or may be interchangeable if the same orsimilar elements and code is used.

At step 406, a user from the onboarded users is determined to beperforming a checkout. This may be detected from a URI or URL entered toa web browser and/or accessed through a different device application(e.g., a resident local application for the device). The address for thecheckout webpages and/or processes may cause the extension and/orapplication to execute, request, and/or fetch a script for the merchantwebsite and/or checkout process from an online transaction processorproviding gift card purchasing services for exact amount digital giftcards. A script is then used to monitor the parsed elements from the DOMtree. At step 408, a DOM tree for the merchant website is determined andparsed for checkout elements. For example, the DOM tree may correspondto a hierarchy for the website that identifies the components andelements on the webpages of the website. The DOM tree may be parsed sothat the elements required to be monitored are identified. Thereafter,at step 410, the checkout elements are monitored for a transactiontotal. This may include determining when the elements and/or codesnippets are present and utilized for proper data entry and processingto determine a transaction total. For example, the elements may requirea shipping total, tax, tip, and other required information to determinethe transaction total is finalized.

At step 412, after the monitoring, the transaction total is detected onthe merchant website. For example, a total may be detected when theinput and processing on the merchant website is completed to a pointwhere a final total is being requested and no additional costs arerequired to be added to the transaction. This may be detected based onthe monitored elements and code snippets. Thus, at step 414, an exactamount gift card for the transaction total is determined. The exactamount gift card may correspond to a digital card purchased and issuedfrom a gift card network, such as a third-party integration with thenetwork and/or a merchant issuing system. The exact amount gift card maybe for a discounted rate over the gift card balance or value, which maybe based on integrations with different third-parties and/or merchants.

At step 416, the exact amount gift card is populated within a window forthe transaction total. For example, a window may be displayed with thetransaction total that shows the exact amount or value for the balanceof the digital gift card (e.g., the transaction total). Further, thewindow may show any savings or additional costs from purchasing the giftcard over the gift card network. Within the window, an option, button,menu, and/or field may be provided to initiate a transaction to purchasethe exact amount gift card. For example, the user may be required toselect or link a funding source, which may then be used to issue apayment for the exact amount gift card. Thus, at step 418, if the exactamount gift card is purchased, the exact amount gift card is applied tothe transaction total. For example, gift card information (e.g.,identifiers, security codes, etc.) may be displayed within the windowfor the digital gift card. An operation of the extension and/orapplication may also automatically apply and/or enter the gift cardinformation to one or more interface fields so that the exact amountgift card may be applied to the transaction.

FIG. 5 is a block diagram of a computer system suitable for implementingone or more components in FIG. 1, according to an embodiment. In variousembodiments, the communication device may comprise a personal computingdevice (e.g., smart phone, a computing tablet, a personal computer,laptop, a wearable computing device such as glasses or a watch,Bluetooth device, key FOB, badge, etc.) capable of communicating withthe network. The service provider may utilize a network computing device(e.g., a network server) capable of communicating with the network. Itshould be appreciated that each of the devices utilized by users andservice providers may be implemented as computer system 500 in a manneras follows.

Computer system 500 includes a bus 502 or other communication mechanismfor communicating information data, signals, and information betweenvarious components of computer system 500. Components include aninput/output (I/O) component 504 that processes a user action, such asselecting keys from a keypad/keyboard, selecting one or more buttons,images, or links, and/or moving one or more images, etc., and sends acorresponding signal to bus 502. I/O component 504 may also include anoutput component, such as a display 511 and a cursor control 513 (suchas a keyboard, keypad, mouse, etc.). An optional audio/visualinput/output (I/O) component 505 may also be included to allow a user touse voice for inputting information by converting audio signals and/orinput or record images/videos by capturing visual data of scenes havingobjects. Audio/visual I/O component 505 may allow the user to hear audioand view images/video including projections of such images/video. Atransceiver or network interface 506 transmits and receives signalsbetween computer system 500 and other devices, such as anothercommunication device, service device, or a service provider server vianetwork 150. In one embodiment, the transmission is wireless, althoughother transmission mediums and methods may also be suitable. One or moreprocessors 512, which can be a micro-controller, digital signalprocessor (DSP), or other processing component, processes these varioussignals, such as for display on computer system 500 or transmission toother devices via a communication link 518. Processor(s) 512 may alsocontrol transmission of information, such as cookies or IP addresses, toother devices.

Components of computer system 500 also include a system memory component514 (e.g., RAM), a static storage component 516 (e.g., ROM), and/or adisk drive 517. Computer system 500 performs specific operations byprocessor(s) 512 and other components by executing one or more sequencesof instructions contained in system memory component 514. Logic may beencoded in a computer readable medium, which may refer to any mediumthat participates in providing instructions to processor(s) 512 forexecution. Such a medium may take many forms, including but not limitedto, non-volatile media, volatile media, and transmission media. Invarious embodiments, non-volatile media includes optical or magneticdisks, volatile media includes dynamic memory, such as system memorycomponent 514, and transmission media includes coaxial cables, copperwire, and fiber optics, including wires that comprise bus 502. In oneembodiment, the logic is encoded in non-transitory computer readablemedium. In one example, transmission media may take the form of acousticor light waves, such as those generated during radio wave, optical, andinfrared data communications.

Some common forms of computer readable media includes, for example,floppy disk, flexible disk, hard disk, magnetic tape, any other magneticmedium, CD-ROM, any other optical medium, punch cards, paper tape, anyother physical medium with patterns of holes, RAM, PROM, EEPROM,FLASH-EEPROM, any other memory chip or cartridge, or any other mediumfrom which a computer is adapted to read.

In various embodiments of the present disclosure, execution ofinstruction sequences to practice the present disclosure may beperformed by computer system 500. In various other embodiments of thepresent disclosure, a plurality of computer systems 500 coupled bycommunication link 518 to the network (e.g., such as a LAN, WLAN, PTSN,and/or various other wired or wireless networks, includingtelecommunications, mobile, and cellular phone networks) may performinstruction sequences to practice the present disclosure in coordinationwith one another.

Where applicable, various embodiments provided by the present disclosuremay be implemented using hardware, software, or combinations of hardwareand software. Also, where applicable, the various hardware componentsand/or software components set forth herein may be combined intocomposite components comprising software, hardware, and/or both withoutdeparting from the spirit of the present disclosure. Where applicable,the various hardware components and/or software components set forthherein may be separated into sub-components comprising software,hardware, or both without departing from the scope of the presentdisclosure. In addition, where applicable, it is contemplated thatsoftware components may be implemented as hardware components andvice-versa.

Software, in accordance with the present disclosure, such as programcode and/or data, may be stored on one or more computer readablemediums. It is also contemplated that software identified herein may beimplemented using one or more general purpose or specific purposecomputers and/or computer systems, networked and/or otherwise. Whereapplicable, the ordering of various steps described herein may bechanged, combined into composite steps, and/or separated into sub-stepsto provide features described herein.

The foregoing disclosure is not intended to limit the present disclosureto the precise forms or particular fields of use disclosed. As such, itis contemplated that various alternate embodiments and/or modificationsto the present disclosure, whether explicitly described or impliedherein, are possible in light of the disclosure. Having thus describedembodiments of the present disclosure, persons of ordinary skill in theart will recognize that changes may be made in form and detail withoutdeparting from the scope of the present disclosure. For example, whilethe description focuses on gift cards, other types of funding sourcesthat can be used to fund a transaction and provide additional value fortheir purchase are also within the scope of various embodiments of theinvention. Thus, the present disclosure is limited only by the claims.

1. A system comprising: a non-transitory memory; and one or morehardware processors coupled to the non-transitory memory and configuredto read instructions from the non-transitory memory to cause the systemto perform operations comprising: determining, for a merchant web siteof a merchant, a webpage parsing script of a browser extension for aplurality of elements on webpages of the merchant website, wherein thewebpage parsing script is implemented by the system from a softwaredevelopment kit of the system for a plurality of merchant websitesincluding the merchant website of the merchant; executing the webpageparsing script with the merchant website; detecting, via the browserextension on a computing device of a user, that the computing device isperforming a checkout for a transaction on the merchant website for themerchant; determining a document object model (DOM) tree for themerchant web site, wherein the DOM tree comprises the plurality ofelements on one or more webpages of the merchant website; parsing theDOM tree for the plurality of elements; monitoring the plurality ofelements using a text monitoring script for transaction data having atleast one amount entered for the transaction to the plurality ofelements; identifying a checkout total for the transaction during thecheckout based on the transaction data; determining the checkout totalis finalized for the transaction based on the monitoring and theidentifying the checkout total; determining a gift card value with themerchant for the checkout total; and causing to be displayed, on thecomputing device in an interface associated with the checkout, the giftcard value for the transaction during the checkout.
 2. The system ofclaim 1, wherein the operations further comprise: receiving a request topurchase the gift card value from the computing device via the browserextension; determining an account for the user that is associated withthe browser extension; processing a payment for the gift card valueusing the account; and providing the gift card value to the user for thecheckout total using the browser extension.
 3. The system of claim 2,wherein the gift card value comprises an exact amount for the checkouttotal, and wherein the payment for the gift card value comprises adiscount from the checkout total.
 4. The system of claim 1, wherein themonitoring the plurality of elements is performed at one of continuouslyat a predefined time interval or in response to at least one of a website navigation on the merchant website or an input to the checkout onthe merchant web site.
 5. The system of claim 1, wherein the textmonitoring script executes a Javascript set that passes monitoringinstructions for a subset of the plurality of elements of the DOM treeselected for the monitoring.
 6. The system of claim 1, wherein theplurality of elements comprise DOM elements associated with snippets ofhypertext markup language (HTML) code for the merchant website.
 7. Thesystem of claim 1, wherein prior to the determining the checkout totalis finalized, the operations further comprise: determining at least oneadditional discount for the transaction; and applying the at least oneadditional discount to the transaction, wherein the checkout totalcomprises a reduced amount for the transaction based on the at least oneadditional discount.
 8. The system of claim 7, wherein prior to theapplying, the operations further comprise: prompting, on the computingdevice via the browser extension, the user of whether to enter the atleast one additional discount for the transaction; receiving a requestto enter the at least one additional discount from the computing devicevia the browser extension; and automatically entering the at least oneadditional discount to a discount field for at least one of theplurality of elements.
 9. The system of claim 7, wherein the determiningthe checkout determine total is finalized comprises checking at least asubset of the plurality of elements for at least one of the transactiondata or user shipping data entered to the at least the subset of theplurality of elements after the applying the at least one additionaldiscount to the transaction.
 10. The system of claim 1, wherein thedetermining the checkout total is finalized comprises determining thecheckout total from a webview of the merchant website, wherein thewebview is associated with a webpage flow for the plurality of elementsof the merchant website.
 11. The system of claim 1, wherein the textmonitoring script is specific to a uniform resource indicator (URI) forone or more HTML pages or Extensible Markup Language (XML) pages of themerchant website.
 12. A method comprising: receiving, from anapplication on a computing device of a user, a webview of a checkoutwebpage on a website for a merchant, wherein the webview comprisestransaction data for a transaction processed through the checkoutwebpage; determining, for the website, a webpage parsing scriptimplemented with the application from a software development kit for aplurality of websites including the website; executing the webpageparsing script with the website; parsing a document object model (DOM)for at least the checkout webpage based on the executing; identifying,based on the parsing, webpage elements selected for monitoring when afinal checkout amount is completed on the checkout webpage, wherein thewebpage elements comprises data fields for entry of checkout data forthe checkout webpage, and wherein the checkout data comprisestransaction data having one or more transaction amounts entered to thewebpage elements; determining, using a webpage parsing script configuredto monitor the webpage elements, that the final checkout amount iscompleted on the checkout webpage based on the transaction data for thewebpage elements; determining a value for a digital gift card availablewith the merchant, wherein the value is associated with at least aportion of the final checkout amount; and outputting the value for thedigital gift card on the computing device using the application.
 13. Themethod of claim 12, further comprising: processing a gift cardtransaction to purchase the value for the digital gift card; and atleast one of: (a) providing a digital code for the digital gift card tothe user via the application; or (b) automatically entering the digitalcode to a field on the checkout webpage using the application.
 14. Themethod of claim 13, wherein the transaction comprises an item total forthe final checkout amount and a tip amount option applied to thetransaction after the final checkout amount, and wherein the methodfurther comprises: after the processing the gift card transaction,providing the tip amount option on the computing device using theapplication, wherein the tip amount option comprises an option topurchase an additional value for an additional digital gift card for atip applied to the transaction.
 15. The method of claim 12, wherein theapplication comprises a mobile application and the computing devicecomprises a mobile device, and wherein the checkout webpage is displayedvia the mobile application when accessing the website through the mobileapplication.
 16. The method of claim 15, wherein the parsing the DOM isperformed by a service provider associated with the mobile application,and wherein the webpage elements selected for monitoring are establishedby the service provider specifically for the website of the merchant.17. The method of claim 12, wherein the value comprises a maximum fixedvalue for the digital gift card allowed by the application, and whereinthe value for the portion is less than the final checkout amount. 18.The method of claim 12, wherein a cost for a purchase of the digitalgift card for the value comprises a discount from the value of thedigital gift card based on an integration of a service providerassociated with the application with the merchant.
 19. A non-transitorymachine-readable medium having stored thereon machine-readableinstructions executable to cause a machine to perform operationscomprising: determining, for a website of a merchant, a text monitoringscript of a browser extension implemented with the browser extensionfrom a software development kit for a plurality of websites includingthe website of the merchant; executing the text monitoring script withthe website; monitoring, using the browser extension for a browser on adevice of a user, hypertext markup language (HTML) code snippets fordomain object model (DOM) elements associated with for transaction data,a shipping amount, and a tax amount for the transaction from the DOMelements on the website of the merchant using the text monitoringscript; detecting, using the browser extension, that a final total hasbeen entered for electronic transaction based on the monitoring thetransaction data, the shipping amount, and the tax amount; determining agift card value for the merchant that is available to be applied for anamount of the final total; causing to be displayed, with the website bythe browser extension, the gift card value with a browser operation thatenables purchasing of the gift card value; receiving, from the browserextension, a request to purchase the gift card value; processing apayment for the gift card value using an account of the user associatedwith the browser extension on the device; and applying the gift cardvalue to the electronic transaction.
 20. The non-transitorymachine-readable medium of claim 19, wherein the text monitoring scriptis specific to the website of the merchant based on the DOM elements forthe website, and wherein prior to the applying the gift card value tothe electronic transaction, the operations further comprise at least oneof: (a) causing to be displayed, by the browser extension, a cardidentifier for the gift card value; or (b) automatically entering, usingthe browser extension, the card identifier to a gift card fieldassociated with the electronic transaction on the website.